5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
- Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-4: Understanding Process Design

The Input Process


An input process allows users to enter, modify, delete, and inquire about data in an application. Included in the basic information you provide for an input process is the Process Control File (called the PCF) associated with the process. For example, the PCF for a customer file maintenance input process would be the CUSTOMER file. Each input process can have at most one PCF.

Each input process consists of one or more frames (refer to the description of process components later in this chapter). For example, if a file has more input items than will fit on a single screen, you can define two frames that operate one after the other so the users can enter all of the required information.

Each frame may have one or more alternate images (also described in more detail later), which are the screen representations that appear to the users. If more than one image has been defined, one of them is selected to display based on previous user input.

A complete input process provides many different event points (described later) at which you can incorporate an ILF routine (set of statements) to supplement the basic process specifications. For example, you may want to calculate an extended price based upon the unit price and the quantity entered by a user.

As with a menu process, you paint the images that are to appear in an input process. Within the context of the Image Editor, you specify where each input item (user-entered field) is to appear. APPX automatically references the data dictionary to validate each item you paint, and displays the field as a series of either 'pseudo blanks' for Character Modes applications, or a rectangle widget using the GUI client, based on its length defined in the dictionary. The image editor also allows you to define any of several characteristic attributes. These characteristics variy widely depending upon the presentation mode (client) you are using.

Although the data dictionary already contains information about how a field should be formatted on an image (its default display mask), you can override this on each image. For example, you may want to display a date field, normally displayed as '12/31' (MM/DD), as 'December 31'.

There are many other optional or automatic features provided in an input process including:

Data lookup to retrieve and optionally display data from another related file (such as, in an order entry process, using a CUSTOMER ID to look up and display a name from the CUSTOMER file).

Automatic retrieval of the next record on the file each time a user completes an input action.

Partial key option, by which you designate whether a user can enter a partial key or needs to enter a full key to identify a record on file.

Automatic update and/or deletion of records in related files. If so specified, APPX effectively allows a user to change key values in one or several associated files.

Automatic field validation against the data dictionary when data is entered by a user.

Scrolling of records. Each frame and a selected alternate image may appear once or, you can specify that it scrolls. APPX supports both vertical and horizontal scrolling.

Refer to Input Processes for detailed specifications on defining these processes.

Application Design Manual                                         "Powered by Appx Software"

66

©2006 By APPX Software, Inc. All Rights Reserved